-
Notifications
You must be signed in to change notification settings - Fork 17
Add Edits From NPD Repo #343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Isaac Milarsky <[email protected]>
Signed-off-by: Isaac Milarsky <[email protected]>
Signed-off-by: Isaac Milarsky <[email protected]>
Signed-off-by: Isaac Milarsky <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After resolving the secrets variable error, this should be good to go!
Another question: does the .gitleaks.toml file have to live in the root directory? Could this be moved to the .github directory?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM +1 🚢
This blocking on anything else?
Signed-off-by: Isaac Milarsky <[email protected]>
Sounds good! I have updated the raw tag problem finally. As for the .gitleaks.toml question, we could move it into the .github directory however we would have to configure gitleaks to look for the file in that location explicitly. I have amended the gitleaks workflow to look for the config in that location and moved the files accordingly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and all is working!! LGTM 🙌
Super clutch, thank you! |
Add Edits From NPD Repo
Problem
Currently, we have issues with our contributors.yml workflow. We also do not have a default
.gitleaks.tomlfile template that we include in the repositories that are generated.Solution
In the contributors.yml file, use a personal access token in the checkout action to make sure that we are using a user that has push access to main. This way we can circumvent branch protections for the action.
Also, added a
.gitleaks.tomlfile to all tiers as well as this repository. This file includes gitleaks regex patterns for common keys. It can and should be configured for different project types.